CVE-2026-0500
Remote code execution in SAP Wily Introscope Enterprise Manager (WorkStation)
Description
Due to the usage of vulnerable third party component in SAP Wily Introscope Enterprise Manager (WorkStation), an unauthenticated attacker could create a malicious JNLP (Java Network Launch Protocol) file accessible by a public facing URL. When a victim clicks on the URL the accessed Wily Introscope Server could execute OS commands on the victim's machine. This could completely compromising confidentiality, integrity and availability of the system.
INFO
Published Date :
Jan. 13, 2026, 2:15 a.m.
Last Modified :
Jan. 22, 2026, 6:47 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | CRITICAL | e4686d1a-f260-4930-ac4c-2f5c992778dd | ||||
| CVSS 3.1 | CRITICAL | [email protected] | ||||
| CVSS 3.1 | HIGH | [email protected] |
Solution
- Update the vulnerable third-party component in SAP Wily Introscope.
- Remove access to malicious JNLP files.
- Educate users about suspicious links.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-0500.
| URL | Resource |
|---|---|
| https://me.sap.com/notes/3668679 | Permissions Required |
| https://url.sap/sapsecuritypatchday | Patch Vendor Advisory |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-0500 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-0500
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-0500 vulnerability anywhere in the article.
-
Daily CyberSecurity
Critical SAP Alert: S/4HANA SQL Injection & Wily RCE Threaten Financial Data
SAP administrators are facing a busy start to the year. On January 13, 2026, the enterprise software giant released 17 new security notes, addressing a raft of vulnerabilities that could expose critic ... Read more
The following table lists the changes that have been made to the
CVE-2026-0500 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Jan. 22, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Added CPE Configuration OR *cpe:2.3:a:sap:introscope_enterprise_manager:10.8:*:*:*:*:*:*:* Added Reference Type SAP SE: https://me.sap.com/notes/3668679 Types: Permissions Required Added Reference Type SAP SE: https://url.sap/sapsecuritypatchday Types: Patch, Vendor Advisory -
New CVE Received by [email protected]
Jan. 13, 2026
Action Type Old Value New Value Added Description Due to the usage of vulnerable third party component in SAP Wily Introscope Enterprise Manager (WorkStation), an unauthenticated attacker could create a malicious JNLP (Java Network Launch Protocol) file accessible by a public facing URL. When a victim clicks on the URL the accessed Wily Introscope Server could execute OS commands on the victim's machine. This could completely compromising confidentiality, integrity and availability of the system. Added CVSS V3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H Added CWE CWE-94 Added Reference https://me.sap.com/notes/3668679 Added Reference https://url.sap/sapsecuritypatchday